home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970326-19970626
/
000193_news@newsmaster….columbia.edu _Wed May 14 20:02:15 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id UAA02941
for <kermit.misc@watsun.cc.columbia.edu>; Wed, 14 May 1997 20:02:15 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id UAA11377
for kermit.misc@watsun; Wed, 14 May 1997 20:02:14 -0400 (EDT)
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: K95 problem with logging session
Date: 15 May 1997 00:02:13 GMT
Organization: Columbia University
Lines: 39
Message-ID: <5ldjq5$7a4$1@apakabar.cc.columbia.edu>
References: <33787950.5951997@news.uoguelph.ca> <gerlachEA4Ky6.KHq@netcom.com> <337a1a61.7943489@news.uoguelph.ca>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:7025
In article <337a1a61.7943489@news.uoguelph.ca>,
Leon Loo <lloo@POBoxes.com.X> wrote:
: On Tue, 13 May 1997 15:13:18 GMT, gerlach@netcom.com (Matthew H.
: Gerlach) wrote:
: >A peer at work has mentioned a similar problem to me, but I have not
: >verified it myself. Using Kermit 95, I think ver 1.1.10, he says he cannot
: >log to a directory if the directory name startes with decimal digits,
: >as opposed to characters a-z. It might be that kermit cannot open a file
: >whose name starts with digits.
:
: I originally ran into the problem with version 1.1.7 and upgraded to
: 1.1.11 hoping it would have been fixed. It was not.
:
I posted an answer to this one days ago -- maybe it didn't make it?
Here it is again:
When referring to a file that does not yet exist, the "\nnn" (nnn being
digits) notation is ambiguous. Does it mean, literally, (in this case)
"\123", or is it a backslash-escape, which (in this case) evaluates to the
character '{'?
The manual lists numerous ways to handle such situations. In this case,
the simplest is to use the "other" slash:
log session c:/123
Others include:
log session c:\\123
or:
set command quoting off
log session c:\123
set command quoting on
etc.
- Frank